fix(deps): bump opencode version pins 1.18.3 → 1.18.11 - #288
Merged
Conversation
The MCP SDK v2 "stateless" work shipped transiently in v1.18.8 and was fully reverted in v1.18.9, so 1.18.11 runs the legacy v1 SDK — a drop-in upgrade with zero MCP config schema changes. Aligns the repo's version pins with the runtime actually in use. - Dockerfile ARG, docker-compose default, .env.example -> 1.18.11 - .opencode/package.json plugin bump is local-only (gitignored) - test_mcp_count_consistency.bats: 3/3 pass (count 26, auto-start 6)
darellchua2
added a commit
that referenced
this pull request
Aug 3, 2026
…289) Three decision-supporting research reports from the 1.18.11 upgrade investigation: - research-opencode-11811-stateless-mcp.md — confirms no "stateless MCP" feature exists in 1.18.11 (MCP SDK v2 shipped transiently in v1.18.8, fully reverted in v1.18.9). 1.18.3 -> 1.18.11 is non-breaking. - mcp-11811-implementation-audit.md — per-server MCP audit (26 servers); zero required config changes, only version-pin bumps (applied in #288). - research-zai-glm-5v-turbo-opencode-access.md — glm-5v-turbo is reachable via the standard zai provider (models.dev), NOT coding-plan access; the coding-plan catalog carries only 4 coding models. Co-authored-by: Chua Khiong Kiat - SilentXTwilight <darellchua2@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns the repo's OpenCode version pins with the runtime actually in use (1.18.11). The repo was pinned to
1.18.3while running1.18.11.Why this is a drop-in (no MCP migration)
Research confirmed the "stateless MCP server" upgrade does not exist in 1.18.11. The MCP SDK v2 / streamable-HTTP work shipped transiently in v1.18.8 (PR #39247) and was fully reverted in v1.18.9 (PR #39373) back to
@modelcontextprotocol/sdk@1.29.0— the revert explicitly fixed an Atlassian OAuth issuer mismatch. So 1.18.11 runs the legacy v1 SDK; the only 1.18.11 MCP change is an SSE reconnect-loop stability fix.No MCP config schema changes, no
mcp-remotebridge migration, no new config keys. All 26 MCP entries remain valid as-is.Changes
opencode_app/DockerfileARG OPENCODE_VERSION1.18.3→1.18.11docker-compose.yml1.18.3→1.18.11.env.example1.18.3→1.18.11Verification
test_mcp_count_consistency.bats: 3/3 pass — MCP count stays 26, auto-start stays 6, markitdown present + disabled.Not in scope (deferred)
mcp-remote→ nativetype: "remote"migration (defer until OpenCode re-lands SDK v2; native OAuth path regressed and was reverted).permission.read: { "mcp:*": "deny" }workaround kept (visibility-bug fix status unverified in 1.18.11).Full research reports in
research/(untracked).🤖 Generated with opencode